Method and structure for variable-length frame support in a shared memory switch

ABSTRACT

The present invention relates to switching in electronic networks. Many data transmission protocols and technologies used in such networks, such as TCP/IP and Ethernet, use variable-length packets for transmission. Often however, the nodes that make up these networks typically contain high-speed cell switches that only support fixed-size data units. To support variable-length packets in such a fixed-size cell switch non-interleaving switching and transmission must be offered. The present invention provides such a solution in essence by segmenting a variable-length frame into a plurality of fixed-length cells including a start-of-frame cell, one or more continuation cell(s), and an end-of-frame cell and routes said fixed-length cells through said switch, thereby providing, at an output of said switch, subsequent and deadlock-free transmission of consecutive cells of a certain frame, and block any cell of a different frame from interleaving. This leads to better average delay characteristics and removes the need for packet reassembly.

FIELD OF THE INVENTION

[0001] The present invention relates to switching in electronic networks. Many data transmission protocols and technologies used in such networks, such as TCP/IP and Ethernet, use variable length packets as their transmission units. However, the nodes that make up these networks typically contain high-speed cell switches that only support fixed-size data units. It would be desirable to support variable length data units in such a fixed-size cell switch by offering non-interleaving switching and transmission of such data units. This would remove the need for packet reassembly and lead to better average delay characteristics.

[0002] Additionally, many such networks use so-called multicast, i.e. the duplication of one incoming data unit to multiple outputs, and Quality-of-Service (QoS) provisioning, i.e. service differentiation among classes of traffic, as important functions. Consequently, multicast and QoS support must today be offered by any switching fabric.

INTRODUCTION AND PRIOR ART

[0003] A common implementation of high-speed cell switches, e.g. as described by W. E. Denzel, A. P. J. Engbersen, and I. Iliadis in “A Flexible Shared-Buffer Switch for ATM at Gb/s Rates”, published in Computer Networks and ISDN Systems, Vol. 27, No. 4, Jan. 1995, pp. 611-624, adopts an output-queued, shared-memory approach. Integrating the functions of multicast, QoS support, and variable-length data units in such an architecture entails a number of possible deadlock scenarios, which must be addressed in order to prevent switch operation from being stalled indefinitely.

[0004] The method described presently builds on top of fixed-length cell switches and is completely orthogonal to any other feature in such a switch. That is, it does not harm the performance in terms of latency or throughput, if used as conventional cell based switch. It is also orthogonal to the both the multicast functionality and the QoS functionality, e.g. traffic priorities, that is addressed in such switches.

[0005] An existing architecture describe C. B. Stunkel et al in “Implementing Multidestination Worms in Switch-based Parallel Systems: Architectural Alternatives and their Impact”, Proceedings of the 24th ACM Annual International Symposium on Computer Architecture (ISCA '97), June 1997, Denver, Colo., USA. They disclose several ways to implement what they call “multidestination worms”, which are somewhat similar to multicast frames discussed here. Their preferred solution is a hybrid central buffer/crossbar solution, although the crossbar is really only used to route unicast traffic with low latency. To avoid deadlocks, Stunkel et al take the approach to assure in advance that a frame can be stored in its entirety in the shared buffer. The head-of-frame is not admitted into the switch before this condition is met. This does not imply that, at the time of admittance, there is sufficient space to fit the entire frame, but eventually, through frames exiting the switch, there will be enough space freed to store the entire frame.

[0006] A drawback of this approach is that the shared buffer must be at least as large as the largest frame to be switched, which is a rather undesirable and hardly foreseeable restriction.

[0007] To achieve the above objectives, i.e. to reduce the delay and avoid the need for reassembling variable length packets in a switch with fixed-length cells, the present invention essentially aims at

[0008] offering a deadlock-free support for a variable-length packet mode frame mode hereinafter),

[0009] extending this frame mode with multicast support in a deadlock-free fashion, and

[0010] enhancing this frame mode with multiple priorities, such that frames of higher priority destined to the same output may preempt the current frame, but not if they are of the same or lower priority.

[0011] Thus, the present invention uses resources more efficiently because the shared buffer or shared memory does not have to be as large to store an entire frame as the above described approach by Stunkel et al.

[0012] In other words, the present invention enhances fixed-length cell switches to support also variable-length packets, a packet being composed of a plurality of cells, such that the switch can be used as a conventional fixed-length cell switch without any disadvantages. Thus, the present invention enables a conventional fixed-length cell switch to be used in ATM networks as well as multiprocessor message passing environments, such as SP2 type of environments, that are typically used for parallel computation. To summarize, the great benefit of the present invention is that it unifies different switch designs tailored for different type of networks into one single architecture.

THE INVENTION

[0013] For the above objectives, the invention provides a solution by providing a novel approach as well as suggested embodiments, i.e. a practical hardware implementation, which—at a modest cost in terms of additional hardware—combines the concepts of both multicast and frame mode in an elegant manner and preferably in a single-chip switch fabric, based on an output-queued, shared memory architecture, while sacrificing none of the performance advantages of such an architecture.

[0014] The major advantages of the approach according to the invention are the seamless integration, from a switching point of view, of unicast and multicast frames, and the cost-efficient merging of three highly desirable features into one switching fabric.

[0015] Whereas the traditional cell switch's application range was usually quite limited, the addition and integration of both frame mode and multicast functionality enables this type of switch fabric to find applications in a wide range of products:

[0016] the traditional ATM world,

[0017] the router world (native support for variable length TCP/IP packets),

[0018] the Ethernet world (native support for variable length Ethernet frames),

[0019] the (mainframe) server world (as a high-speed interconnect to cluster servers together, instead of the traditional mesh), and/or

[0020] the parallel processing world (as a replacement for the traditional bus structure to interconnect processors and memory).

[0021] In the description below, the following expression notation will be used:

OP (i:range(i):expr(i));

[0022] where OP can be any binary operator, i is a dummy variable, range(i) expresses a range (and/or condition) for variable i, and expr(i) can be any expression, usually also a function of i. This notation is shorthand for

expr(i₀)op expr(i₁)op . . . expr(i_(n−1))op expr(i_(n))

[0023] where i₀ through i_(n) are the values of i that satisfy the range(i) condition.

THE SYSTEM

[0024]FIG. 1 displays the system level architecture. We assume a system dimension of N inputs×N outputs, i.e. N×N, although the invention is not limited to systems with equals numbers of inputs and outputs. At the input side, variable-length data units arrive and are segmented into fixed-length cells by the segmentation units. These cells are forwarded to the input queues, where they are stored according to their destination. This is often called “virtual output queuing”, VOQ. The input queue arbiter makes a decision on which start-of-frame cell to forward, taking into account OQ grant and memory grant information. This system is described by C. Minkenberg, A. P. J. Engbersen, and M. Colmant in “A Robust Switch Architecture for Bursty Traffic”, published in Proc. Int. Zurich Seminar on Broadband Communication IZS 2000, Zurich, Switzerland, Feb. 15-17, 2000, pp. 207-214.

[0025] Strict first-in-first-out, FIFO order of cells destined to the same output and of the same priority must be maintained in order to guarantee frame integrity. Although not mandatory for correct system operation, it is recommended that frames are transmitted from the input queue without interleaving of cells from frames to other outputs, that is, once a start-of-frame cell has been selected, the input queue forwards the corresponding continuation and end-of-frame cells in subsequent time slots, again always taking grant information into account. Other start-of-frame cells are only considered for transmission once the current frame has been completed, i.e. just after an end-of-frame cell has been transmitted.

[0026] Cells are forwarded to the switch, which routes them to their proper destination(s). The cells emerging at the egress side of the switch are then reassembled into frames by the reassembly units. In case frame mode is enforced, this unit will have no functionality, except perhaps stripping off the switch's internal cell headers. The internal organization of the switch is such that the control section only handles memory addresses, while the data is passed through the shared memory, as described by W. E. Denzel, A. P. J. Engbersen and I. Iliadis in “A Flexible Shared-Buffer Switch for ATM at Gb/s Rates”, published in Computer Networks and ISDN Systems, Vol. 27, No. 4, January 1995, pp. 611-624.

[0027] The shared memory configuration is known to be well suited for implementation of multicast transmission—the data is stored only once, while the corresponding address is duplicated to all destination queues. A counter associated with the memory address, initially set to the number of copies to be transmitted, is decremented for every copy that leaves the switch, and the address is only released when the counter reaches zero, i.e. the last copy has left the switch.

[0028] The switch employs a flow control mechanism consisting of two signals:

[0029] a shared memory grant G_(i;SM), based on memory occupancy O_(SM). When the memory fill exceeds a programmable threshold T_(SM), the shared memory grant is removed. The input queues are not allowed to send any more cells as soon as they detect this condition. Note that, for now, the shared memory grant is not actually a function of the input i.

G _(i;SM) :=O _(SM) <T _(SM), where 0≦i<N.  (1)

[0030] a per-destination grant G_(i)(j), based on output queue occupancy O_(Q)(j). This is a vector of size N, of which bit j corresponds to the status of output queue j. When the output queue fill exceeds a programmable threshold T_(Q)(j), the corresponding output-queue grant is removed by resetting the corresponding bit in the per-destination grant vector. When the input queues detect this condition, they will not send any more cells destined to this output.

G _(i)(j)=O _(Q) <T _(Q)(j), where 0≦i,j<N.  (2)

[0031] Note that the terms “per-destination grant” and “output-queue grant” are used interchangeably.

[0032] Additionally, the output queues are assumed to be of such size that one can fit all memory addresses. Cells are always accepted as long as there are shared memory addresses available, regardless of output queue status. The unavailability of a shared memory address is flagged as a fatal error condition, since this would imply the loss of a cell.

THE FRAME MODE

[0033] A frame is defined to be a variable length data unit, equivalent in size to a multiple of the fixed cell size of the switch. In order to transmit a frame, it is segmented into smaller, fixed-length cells, which are subsequently routed through the switch. Thereby, the first cell of a frame is termed the start-of-frame cell, any subsequent cells before the last one continuation cells, and the last one end-of-frame cell. If no additional precautions are taken, cells from different frames (arriving from different inputs) may be interleaved on one output, so that frame reassembly is required. Therefore, it is desirable to transmit frames in a non-interleaved fashion, which leads to better average frame delay characteristics. This mode of operation is henceforth referred to as frame mode.

[0034] Unfortunately, introducing the frame mode leads to a number of possible deadlock conditions, namely:

[0035] output queue deadlock and shared memory deadlock due to unicast traffic,

[0036] shared memory deadlock due to multicast traffic, and

[0037] shared memory deadlock due to multiple traffic priorities.

[0038] In general, these deadlocks occur because an output is waiting for a continuation cell of the frame it is currently transmitting, but this cell cannot enter the switch due to an output queue full or a shared memory full condition.

DETAILED DESCRIPTION OF THE FUNCTION AND OF AN EMBODIMENT

[0039] In the following more detailed description, the function of the invention will be described first. Subsequently, a hardware implementation will be disclosed. This description is supported and completed by the appended drawings which illustrate several examples, namely in:

[0040]FIG. 1 the system level architecture, already discussed above;

[0041]FIGS. 2a-2 c the frame mode deadlock;

[0042]FIG. 3 an active concept unusable for multicast,

[0043]FIG. 4 a cyclic waiting multicast frame deadlock with two frames;

[0044]FIG. 5 a cyclic waiting multicast frame deadlock with three frames;

[0045]FIG. 6 an implementation for a logical output queue;

[0046]FIG. 7 a format for an output queue entry,

[0047]FIG. 8 a comparison of output queue size vs. implementation, and

[0048]FIG. 9 a shared memory with split control and data paths.

UNICAST DEADLOCK PREVENTION

[0049] First, it will be explained how to prevent deadlock conditions from occuring when only unicast traffic (traffic with only a single destination) is considered.

[0050] The output-queue-full deadlock condition occurs when the output queue threshold is crossed while there are no more continuation cells of the current frame in the queue. Since the queue is marked full, they will also not be allowed to enter the switch, hence deadlock occurs.

[0051] The shared memory deadlock is similar. When the shared memory threshold is crossed (the memory is “full”), all inputs are blocked from sending any more cells, possibly preventing the required continuation cells from entering the switch, which in turn prevents the switch from freeing up the memory addresses needed in the first place.

[0052]FIGS. 2a to 2 c illustrate the deadlock. Two very long frames, a first frame 11 and a second frame 12 have the same destination, of which frame 11 is being transmitted. Before frame 11 finishes its output 13, the output queue 10 (or the shared memory) fills up with cells for frame 12, until the queue full threshold (or the shared memory threshold) is crossed, preventing further cells from entering the switch.

[0053] To circumvent these deadlock conditions, the novel concept of active inputs was developed: Definition 1 (Active Concept): An input i is defined as being active with respect to output j when on output j a frame that arrived on input i is being transmitted. The active states are represented by the boolean vectors A_(i)(*). An input is said to be active, represented by A_(i)*, when it is active with respect to at least one output:

A _(i)*:=∃(j:0≦j<N:A _(i)(j)≡true)  (3)

[0054] “Being transmitted” in this sense means that the start-of-frame cell of said frame has been transmitted, while the end-of-frame cell has not yet been. A frame being transmitted is also called an active frame and the output it is being transmitted on is an active output.

[0055] Additionally, an almost full condition is defined for the shared memory. A programmable almost full threshold T_(AF) is compared to the current memory occupancy O_(SM). Assuming a flow control delay equivalent to D cell slots between switch and adapter, this threshold should be programmed smaller or equal to the memory full threshold minus D times the number of ports N:

T _(AF) ≦T _(SM) −D*N.  (3a)

[0056] When the shared memory occupancy is above this threshold, the shared memory is said to be almost full. This threshold is programmed to some value below the actual memory full threshold, satisfying equation (3a).

[0057] Now, compared to the conventional flow control of equations (1) and (2), the outgoing flow control to the adapters is modified as follows for the shared memory grant

G _(i,SM)*:=(

(O _(SM) >T _(AF))νA _(i)*)

(O _(SM) >T _(SM)),  (4)

[0058] while the output queue grants are now determined by

G _(i)(_(j)):=

(O _(Q)(j)≧T _(Q)(j))νA _(i)(j), with 0≦i≦N and 0≦j≦N.  (5)

[0059] Note that this equation does not impose a maximum queue size limit for active inputs. Therefore, the output queue size is assumed to beat least as large as the shared memory.

[0060] The above equations (4) and (5) can be read as follows:

[0061] An input i receives shared memory grant if and only if ((the shared memory is not almost full) OR (input i is marked active)) AND (the shared memory is not full).

[0062] An input i receives output grant for output j if and only if (output queue j has not exceeded its threshold) OR (input i is marked active for output j).

[0063] Note that the switch resorts to a crossbar-like mode of operation when the almost-full threshold is exceeded, because then only one input is allowed to send to an active output, i.e. there is a one-to-one matching between (active) inputs and outputs, just like in a crossbar. Note also that both shared memory grant as well as per-destination grant are determined on a per-input basis now.

[0064] This scheme solves the output queue deadlock because it ensures that the output queue grant for the input that may still have to send the rest of the frame is positive as long as the frame has not been completed, thus allowing it to bypass the output queue full condition. Note that only this input gets a positive grant for this output. The active status for an input must be marked on a per output basis because an input can actually be active for multiple outputs at the same time. If the input queue does not interleave frames to different outputs, it is guaranteed that only one of these frames is not entirely in the switch yet

[0065] Furthermore, this scheme also solves the shared memory deadlock. Recall that this deadlock occurs because the inputs that have the required continuation cells cannot send because the switch is full, and the switch cannot free up memory addresses because it needs those continuation cells. What is achieved by the active scheme is that when the switch is almost full, i.e. close to the full threshold, but there are still some addresses available, those addresses for sure go to the inputs that need them.

[0066] Another way of looking at it is that, when almost full, it is guaranteed that at least as many cells exit the switch as enter, ensuring that the memory occupancy does not grow further, preventing the memory from reaching the full threshold. That the previous statement holds true can easily be seen when realizing that there are never more active inputs than there are frames being transmitted (no output can be busy transmitting frames from more than one input), and hence, in each cycle at least as many cells leave the switch on the active outputs, as enter on the active inputs.

MULTICAST DEADLOCK PREVENTION

[0067] The above approach solves the deadlock problem for the unicast case, in multicast traffic however, another deadlock scenario presents itself. The essence of this new problem is that cell transmission and address recycling are no longer directly coupled, because a cell being transmitted, i.e. leaving the switch, will only free up a memory address when it is the last copy of that cell. In unicast, this always holds true, because there is only one copy to be transmitted, but for multicast cells, the active concept described above is no solution.

[0068] Consider FIG. 3, where two very long frames, a multicast frame 21 and a unicast frame 22 go through the switch, resulting in outputs 23 and 24. Multicast frame 21 is destined for both outputs 23 and 24, unicast frame 22 only for output 24.

[0069] Frame 21 is being transmitted on output 23, frame 22 on output 24. According to the active concept, both inputs 21 and 22 are active, allowing continuation cells from both frames to enter the switch. However, because the cells from multicast frame 21 still need to be transmitted on output 24 as well, their memory addresses are not freed. This causes at least one of the memories 20 or 20′ to fill up with cells for frame 21 until the memory full threshold is crossed, causing the switch to enter a deadlocked state.

[0070] This problem can be solved by introducing the extended active concept, which replaces the active concept of Definition 1.

[0071] Definition 2 (Extended Active Concept): An input i is defined as being active with respect to output j when on this output j a frame that arrived on input i is being transmitted and it is the last copy of the frame. The active states are represented by the boolean vectors A_(i)(j). An input is said to be active, represented by A_(i)*, when it is active with respect to at least one output:

A _(i)*:=∃(j:0≦j<N:A _(i)(j)≡true)  (6, identical to 3)

[0072] The rules for determining the shared memory and output queue grants remain unchanged. Note the addition of the qualification that an input is only marked active if the last copy of the frame is being transmitted. This guarantees that the addresses are really being freed as the cells leave the switch, so that cell transmission and address recycling are once again coupled for active inputs. Also note that this extended definition of the active concept still holds for unicast traffic.

CYCLIC WAITING DEADLOCK

[0073] Unfortunately, the shared memory deadlock is not the only added complication. In order to maintain good switch throughput also under heavy multicast traffic, one must be able to transmit multiple multicast frames in parallel. Since every multicast frame's set of destinations can be any subset of all destinations, this leads to output conflicts. The shared memory, output-queued architecture of the novel switch allows to partially transmit frames, so that not all outputs need to be available before transmission, leading to higher throughput. However, this ability leads to possible deadlock conditions, as shall now be demonstrated.

[0074]FIG. 4 illustrates the following case. Frame 31 from the first input has destinations on output 33 and 34. Frame 32 from the second input also has destinations on these two outputs. Both frames are very long. Frame 31 is active on output 33, frame 32 on output 34. Assumed is that these are the only two frames currently in the switch. Thus, according to Definition 2, neither frame is currently active, the memories 30 and 30′ will fill up, and both will be blocked when the almost full threshold is crossed. At that point, frames 31 and 32 will be mutually waiting for the other's completion, which will never happen because neither is active, disallowing the required continuation cells from entering the switch. Hence, there is a deadlock which is fundamentally different from the shared memory deadlock and which cannot be prevented by the above described extended active concept alone.

[0075] Note that it is not required that frames have at least two destinations in common for the deadlock to occur. Consider a three-frame scenario as depicted in FIG. 5 where frame 41 is destined for outputs 44 and 45, frame 42 goes to 44 and 46, and frame 43 to 45 and 46. Any two frames always have only one destination in common, but when frame 41 is active on output 44, 42 on 46, and 43 on 45, then 42 will be waiting for 41 to end, 41 for 43 to end and 43 for 42 to end, closing the vicious circle. The decision of which frame to send is governed by an arbiter on each output independently. The problem is that these independent decisions may cause cyclic waiting dependencies that cannot be broken once they exist. Therefore, one must prevent these cyclic waiting dependencies from occuring.

[0076] This cyclic dependency can be prevented by imposing a strict ordering rule on the way frames are stored in the output queues. This strict ordering relationship is satisfied if and only if

[0077] a) frames waiting in the same output queue are served in first-in-first-out (FIFO) order according to their arrival times, and

[0078] b) multicast frames that arrive simultaneously at different outputs are stored in the same relative order in all corresponding output queues.

[0079] This guarantees that a unique earliest frame always exists on every output, which does not have to wait for any other frame on any of its destinations. Therefore, cyclic waiting cannot occur and hence the deadlock condition is solved.

FRAME MODE AND PRIORITIES

[0080] Adding QoS support by means of priorities (preemptive, weighted, or otherwise) introduces another dimension to the deadlock problem. We assume P to be the total number of traffic priorities supported by the switch. Every frame has an individual priority p. The ordering relations imposed on frames only apply to frames of the same priority. Frames of different priorities are allowed to be served in any order, decided by some given transmission arbitration scheme. One possibility is to always give precendence to frames of higher priority, so-called strict, or preemptive priorities. Cells of frames of different priorities may even be interleaved at both inputs and outputs.

[0081] Complications arise because frames with different priorities are allowed to be interleaved on an output. It can therefore happen that an output is flagged active on more than one input, but for different priorities. If no additional measures are taken, it can happen that, while in almost full state, cells from multiple frames are allowed to enter the output queue, whereas only one can exit. Thus, the active concept is broken.

[0082] Adding priorities implies that the input status flags have to be kept on a per priority basis, since it can occur that multiple frames are active simultaneously on the same output (one per priority), so the input status arrays from Definition 2 are now indexed per priority as well: A_(p,i)(*). Similarly, the shared memory grant and output queue grant information are provided on a per priority basis as well.

[0083] Switch operation in almost full mode can be restored by only giving grant to the priority for which a cell has left the switch in the current cycle. This is done by keeping track, for every output, from which input and priority a cell was last transmitted.

[0084] Definition 3: (Output Transmit Status) The output transmit status B_(p,j)(i) is defined to be true when a cell of priority p from input i has been transmitted on output j in the current cycle or no cell has been transmitted at all, and false otherwise.

[0085] Definition 4 extends the extended active concept from Definition 2 to incorporate priorities.

[0086] Definition 4: (Transmit Active Concept) An input i is defined as being active with respect to priority p and output j when on output j a frame of priority p that arrived on input i is being transmitted and it is the last copy of the frame. The active states are represented by the boolean vectors A_(p,i)(j). We maintain the notion of “active input”, indicated by A_(p,i)*.

A _(p,i)*:=∃(j:0≦j<N:A _(p,i)(_(j))≡true)  (7)

[0087] Additionally, an input is said to be transmit-active for priority p, represented by A_(p,i)* when it is active with respect to at least one output which is marked active for this priority and input according to Definition 3:

A _(p,i)*:=∃(j:0≦j<N:A _(p,i)(j)≡true

B _(p,j)(i)≡true)  (8)

[0088] The shared memory grant is newly defined by equation (9):

G _(p,i,SM):=(

(O _(SM) >T _(AF))νA _(p,i)*)

(O _(SM) ≧T _(SM))  (9)

[0089] with 0≦p<P, 0≦i<N, 0<j<N.

[0090] Finally, we add a shared memory threshold per priority, thus arriving at equation (10):

G _(p,i,SM):=(((

(O _(p,SM) ≧T _(p,SM))νA _(p,i)*)

(O _(SM) ≧T _(AF))) ν((O _(SM) ≧T _(AF))

A _(p,i)*))

(O _(SM) ≧T _(SM))  (10)

[0091] where O_(p,SM) and T_(p,SM) represent occupancy counters and thresholds per priority, respectively.

[0092] Output-queue grant is transmitted on a per priority basis in a cyclic fashion (one priority per cycle) but is otherwise not affected by adding priorities. The cyclic transmission implies that the output queue grant status on the adapter is updated only once every P cycles, increasing the hysteresis.

G_(p,i)(j):=

(O _(p,Q)(j)≧T _(p,Q)(j))νA _(p,j)(j)  (11)

[0093] Equation (11) assumes programmable thresholds per priority as well as queue occupancy counters per priority, although this is not of importance for the functioning of the deadlock prevention.

[0094] Equations (10) and (11) nicely demonstrate the four different deadlock prevention mechanisms we have introduced:

[0095] The active flag A_(p,i)(j) in equation (11) prevents output queue deadlock.

[0096] The term A_(p,i)* in equation (10) prevents shared memory deadlock on the per priority thresholds.

[0097] The same term also prevents shared memory multicast deadlock by means of the extended active concept (only active when last copy is being processed).

[0098] The term A*_(p,i), also in equation (10), prevents shared memory deadlock when the shared memory is almost full. It incorporates both shared memory multicast deadlock and shared memory priority deadlock prevention.

IMPLEMENTATION

[0099] In the following, some practical considerations with regard to implementations and embodiments will be shown and described.

SHARED MEMORY

[0100] Each shared memory address consists of storage space for one cell, plus an associated multicast counter. Each input controller has an address available in which to store the next arriving cell. When a cell arrives, several things happen:

[0101] the cell data is stored at the available memory address,

[0102] the address is stored in each destination output queue, as indicated by the destination bitmap in the cell's header, and

[0103] the number of destinations is counted and stored in the counter associated with the memory address.

[0104]FIG. 9 illustrates a shared memory implementation with split control and data paths. Cells arrive on a plurality of inputs 91 to be routed to a plurality of outputs 92. The input controllers 93 receive free storage addresses from the address manager 101. These input controllers 93 forward the cell data through an input routing structure 94 that routes the data to the correct location in the shared memory 95. The occupancy counter (not shown) corresponding to this shared memory location is initialized to the number of copies of this cell requested to be sent. The shared memory addresses are forwarded to the output queue access manager 98, that routes them one or more of destination output queues 99, as indicated by the destination information in the cell's header. The addresses are enqueued in the output queues 99. The output queue read manager 100 removes one addresses from each output queue 99 per cell slot, and forwards these addresses to the corresponding output controllers 97, which fetch the corresponding cell data from the shared memory 95 at the address received. The data is forwarded from the shared memory 95 through an output routing structure 96 to the output controllers 97. The addresses are returned to address manager 101, which decreases the corresponding occupancy counter (not shown) by 1 for each address returned. Those addresses for which the occupancy counter has reached zero are released to the free queue to be reused.

FRAME MODE

[0105] The frame mode will be a configurable mode. When enabled, each output keeps track of which frame it is currently processing and will not process any other frames until the current one is completed.

[0106] Each cell carries a flag indicating whether it is a start-of-frame, continuation, or end-of-frame cell. When a start-of-frame cell of priority p, received on input i, is transmitted on output j and it is the last copy of the cell (the associated counter equals one), the output is marked active, and the corresponding bit j is set in the active register A_(p,i). When an end-of-frame cell of priority p, received on input i, is transmitted on output j, the corresponding bit j in register A_(p,i) is cleared, if set.

[0107] When any cell of priority p, received on input i, is transmitted on output j, the corresponding bit is set in the output transmit status register B_(p,j).

[0108] These registers A_(p,i) and B_(p,j), 0≦i,j<N, 0≦p<N, are used to modify the grant signals as described in equations (10) and (11), for the shared memory and output queue grant, resp.

OUTPUT QUEUES

[0109] To enable frame mode, the output queues must maintain order information first to determine the order in which the stored frames are transmitted, and second to maintain the order of start-, continuation-, and end-of-frame cells for each frame. This can be achieved by means of a two-dimensional linked list as shown in FIG. 6. In the first, horizontal dimension, all the start-of-frame cells are linked together In the second dimension, the continuation and end-of-frame cells of the respective frames are linked.

LOGICAL OPERATION

[0110] Every start-of-frame cell, SoF, requires two next-cell pointers, one to the start-of-frame cell of the next frame, and one to the first continuation cell of its own frame. Continuation cells only require one next-cell pointer, namely to the next continuation cell. End-of-frame cells, EoF, require no next-cell pointer at all. Note that a cell may be SoF and EoF simultaneously, if the frame consists of just a single cell.

[0111] Furthermore, every output queue maintains a number of additional pointers to manage its operation:

[0112] a read pointer, which indicates the next cell to be read from the queue,

[0113] a head pointer, which indicates the first SoF cell in the queue,

[0114] a tail pointer, which points to the last SoF cell in the queue, in order to be able to immediately append newly arriving frames (start-of-frame cells) at the right position, and

[0115] an array of N write pointers, one per input, which point to the last cell of any uncompleted frame from the corresponding input (at any given time, only one frame can be incomplete for any input-output pair). Newly arriving continuation cells are appended at the position indicated by the corresponding write pointer.

[0116] All pointers assume the value nil if they are currently invalid. In case multiple priorities are to be supported, one set of all of above-mentioned pointers is required for each priority.

[0117] We assume there is space for Q cells in every output queue OQ, and the queue slots are numbered 0 through Q-1. We assume that a given queue management scheme provides a queue slot q to store an incoming entry. Next, we will describe OQ operation in detail.

[0118] Initially, the output queue is empty and all pointers are nil. When a cell arrives, its memory storage address is passed to the destination output queue, along with the input number the cell arrived on, and the cell type (SoF, CoF, EoF, wherein CoF identifies a continuation cell). Depending on the type of the cell being written, the following three cases must be distinguished:

[0119] SoF: If the OQ is empty, the cell is entered in the queue at slot q, and the head, tail, and read pointers are all set to q. If not, the cell is appended at the tail of the queue as indicated by the tail pointer, i.e., the next SoF pointer of the tail pointer's entry is set toq, and the tail pointer is also set to q. In both cases, the corresponding write pointer is set to q also. This write pointer should be nil; if it isn't, there is an error condition, because the previous frame from the same input has not been completed yet. The last CoF (or SoF, if no CoF is present) should be marked as EoF, to force an end to the incomplete frame. If the head pointer equals nil, it is updated to.

[0120] CoF: the cell is entered in the queue at slot q. If the corresponding write pointer does not equal nil, the cell is linked to the previous cell of its frame by updating the next CoF pointer of the entry indicated by this write pointer, setting it to q, and the write pointer is also updated to q. If the write pointer equals nil, there are two possibilities, depending on the input the cell arrived on. If the input equals the one of the frame that's currently active (if there is one), the cell must belong to that same frame, and both the read pointer and the corresponding write pointer are set to q. Otherwise, there is an error condition, because apparently no SoF or CoF from the same input immediately preceded this cell, nor does it belong to the currently active frame; the incoming cell should then be flagged as SoF, and treated according to the previous bullet to remedy the situation. Additionally, if the OQ is empty, the read pointer is set to q. This can only occur if the cell belongs to the frame currently being transmitted, otherwise there is an error condition. If the new cell's input differs from the one of the frame currently being transmitted, or if there is no frame currently being transmitted, an error must have occurred. All cells from this input up to the next SoF should be discarded.

[0121] EoF: same as CoF, with the addition that the corresponding write pointer is set to nil, to indicate that the frame has been completed.

[0122] OQ read operations are executed as follows. If the read pointer equals nil, no cell is read, i.e., the queue is idle. Note that this is not equivalent to the queue being empty: the queue may be stalled due to absent continuation cells of the frame currently being served. If the read pointer is not nil, the cell indicated by the read pointer is read. Depending on the type of the cell being read, the following three cases must be distinguished:

[0123] SoF: the read pointer is updated to the next CoF entry of the cell. If the next-CoF value equals nil, then the read pointer will also become nil. This happens when a frame has not been completely received yet by the OQ. The tail pointer is set to the cell's next SoF entry (may be nil). The head pointer is updated to the cell's next SoF entry (may also be nil).

[0124] CoF: the read pointer is updated to the next CoF entry of the cell.

[0125] EoF: the read pointer is updated to the value of the head pointer. If the head pointer now equals nil, the tail pointer is also set to nil.

[0126] In all three cases it must additionally be checked whether the queue entry just read is being pointed to by the write pointer of the corresponding input (the input the cell being read arrived on). If this is the case, both the write pointer in question and the read pointer must be set to nil. The OQ also keeps track of the input number of frame currently being transmitted.

[0127]FIG. 6 shows a logical output queue implementation. Frame 1 is currently being transmitted with the read pointer indicating the next cell to be read, while frame 6 is currently being received from input 7, with the corresponding input pointer indicating the last continuation cell of this frame. Note how the start-of-frame cells are linked together in the horizontal direction, with the head and tail pointers indicating the first and last frame in the queue.

PHYSICAL IMPLEMENTATION

[0128] The price paid for supporting frame mode is that every queue entry needs two next-cell pointers, one to point to the next start-of-frame, one to point to the next continuation cell, even though only the start-of-frame cells really need both pointers. FIG. 7 shows the fields that constitute a single entry in an output queue in such a simple implementation. The switch dimension equals N ports, and the shared memory size equals M cells. Every output queue is of size Q, i.e., the queue can store up to Q entries.

[0129]FIG. 7 shows the fields that constitute a single entry in an output queue, i.e. the output queue entry format.

[0130] In this figure, The following table shows the queue entry field sizes field meaning size (bits) A data memory address log₂ M B next start-of-frame address log₂ Q C next continuation cell address log₂ Q D cell type identifier 2 E input identifier log₂ N

[0131] The above sizes of the individual queue entry fields amount to a total of

[0132] (log₂ M+2+log₂ Q+log₂ N+2) bits per entry, for a total of

[0133] NQ(log₂ M+2+log₂ Q+log₂ N+2). This implementation is alternative ‘a’.

[0134]FIG. 8 depicts an example for a shared memory in its upper section and below two varitions of an output queue, displaying the output queue size vs. implementation. The central section shows an output queue for Q<M, wherein Q is the output queue size and M is the shared memory size, and the section at the bottom of the page an output queue of size Q=M.

[0135] The shared memory consists of M packet locations numbered 0 through M-1 as shown. Below, two OQ implementation alternatives are shown. The first OQ implementation has queue size Q smaller than memory size M. The queue slots are numbered 0 through Q-1. This implementation requires two fields per queue entry to build the linked list, namely the memory address of the current entry, and the queue slot of the next queue entry. The second implementation below, with queue size Q=M, requires only the next queue slot to build the linked list, as shown.

[0136] An improvement can be achieved by sizing the output queues up to the shared memory size, Q=M. This may seem wasteful at first, but there are several advantages, which will be explained with the help of FIG. 8.

[0137] First, although the queue has more entries, the individual entries can become smaller, because there is no longer a need to actually store the memory address in the queue by instituting a one-to-one correspondence between the place in the queue and the memory address, which is not possible with a queue that is smaller than the memory. On top of that, a smaller queue will need its own free queue with the associated queue management logic, not shown in FIG. 8. As an example, the figure demonstrates how the sequence of cells {a; b; c; d} is linked up in both implementations. The queue entry size in this implementation equals (2logg₂ M+log₂ N+2) for a total of NM(2log₂ M+log₂ N+2). This implementation is alternative ‘b’.

[0138] Further improvements are possible by observing that SoF entries only require a next-SoF pointer, whereas CoF entries only require a next-CoF pointer. Additionally, the input identifier need only be stored with SoF entries. These observations suggest an implementation where queues for SoF and CoF entries are separated. We can make a large saving by realizing that the order of CoF cells of a given frame is identical on all outputs, by the definition of a frame; that is, CoF order does not have to be maintained on a per-output basis. This implies that only one CoF queue (also of size M) is needed, along with N SoF queues.

[0139] In terms of the previous table this means that the SoF queues store fields B and E, and the CoF queue stores field C. Since the type of cell is already implicit in the queue it is stored in, only a 1-bit cell type identifier to flag EoF cells is required (for entries in all queues).

[0140] The resulting implementation requires NM (log₂ M+log₂ N+1), bits for the SoF queues plus M(log₂ M+1) bits for the CoF queue, for a total of (N+1)M(log₂ M+1)+NM log₂ N bits. This is the final implementation alternative ‘c’.

[0141] The following table compares the implementation complexities of the three proposed alternatives, expressed in the total number of bits of storage required. Implementation Complexity (bits of storage) a(N,Q,M) NQ(log₂ M + 2log₂ Q + log₂ N + 2) b(N,M) NM(2 log₂ M + log₂ N + 2) c(N,M) (N + 1) M (log₂ M + 1) + NM log₂ N

[0142] To avoid cyclic waiting deadlock conditions, a strict enqueuing order must be satisfied. This can be achieved as follows: The output queues follow a strict FIFO discipline on a per frame basis. Frames that arrive at one output queue simultaneously are ordered according to a predetermined order of their respective input numbers. This can be round robin, or any other suitable ordering scheme. The key point in realizing the strict timing order is to make sure that this order is identical at all outputs. However, the order of inputs must not be identical in subsequent time slots. For reasons of fairness, the order may be suitably rearranged at every time slot.

[0143] Thus, the present invention presents a way to integrate support for both frame mode operation and multicast in an output-queue shared memory cell switch. It has been shown how deadlock situation in both unicast and multicast frame mode can be avoided, also an overview of how to implement these schemes has been given.

[0144] While the present invention has been described theoretically and by way of examples, these shall not limit the scope of protection since it is obvious to someone skilled in the art that the invention can be easily adapted to match many requirements in the field of switches and switching fabrics. 

1. A method for providing routing capability for variable-length unit traffic in a fixed-length cell routing switch with a shared memory characterized in that an incoming variable-length unit, a frame, is segmented into a plurality of fixed-length cells including a start-of-frame cell, one or more continuation cell(s), and an end-of-frame cell, said fixed-length cells are routed through said switch, at an output of said switch, subsequent and deadlock-free transmission of consecutive cells of a certain frame is guaranteed by blocking any cell of a different frame from interleaving, which is governed by defining a predetermined first condition for said shared memory, defining a predetermined second condition for said certain frame and its cells, controlling a cell's entry into said shared memory depending upon said first condition, and controlling transmission of a said cell of said certain frame depending upon said second condition.
 2. The method according to claim 1, wherein further a frame to be transmitted is assigned a multicast vector indicating a plurality of outputs of the switch.
 3. The method according to claim 1 or 2, wherein further a frame to be transmitted is assigned a priority and, at an output of the switch, transmission of cells of a frame with a lower priority is interrupted when a frame with a higher priority is to be transmitted at said same output.
 4. The method according to claim 3, wherein transmission of cells of the frame with the lower priority is resumed when the frame with the higher priority is fully transmitted.
 5. The method according to any of the claims 1 to 4, wherein the first condition controls a cell's entry into the shared memory by granting entry if and only if there is space available in said shared memory AND a predetermined “almost full” condition, indicating that a limited memory space is available, is not met in said shared memory OR an “active frame” condition is met, indicating that a certain frame's start-of-frame cell has been transmitted, but not its end-of-frame cell.
 6. The method according to any of the preceding claims, wherein the second condition allows a cell's transmission through the switch to a certain output if and only if the output queue associated to said certain output has not exceeded its pretermined threshold OR said cell is marked “active” for said certain output, i.e. belonging to an “active frame” whose start-of-frame cell has been transmitted, but not its end-of-frame cell.
 7. The method according to claims 5 or 6, wherein each output keeps track which frame is currently “active”, i.e. being transmitted, and will not process any other frame until the end-of-frame cell of said current one is transmitted.
 8. The method according to any of the preceding claims, wherein each cell is assigned a flag indicating whether it is a start-of-frame or continuation or end-of-frame cell.
 9. The method according to claim 5, wherein the “almost full” condition for said shared memory is a programmable threshold below a “memory full” threshold, i.e. the total space available in said memory.
 10. The method according to claim 9, wherein the “almost full” threshold TAF is smaller or equal to the “memory full” threshold TSM minus D times the number of ports N of the switch, T _(AF) <T _(SM) −D·N,  D being the flow control delay in cells in the switch.
 11. The method according to any preceding claim, wherein the second condition controlling a cell's transmission through the switch to a certain output is extended to include multicast deadlock prevention by defining a frame to be “active” if and only if its last copy is being transmitted, so that said second condition allows a cell's transmission if and only if the output queue associated to said certain output has not exceeded its pretermined threshold OR said cell is marked “active” for said certain output, i.e. belonging to the last copy of an “active frame” whose start-of-frame cell has been transmitted, but not its end-of-frame cell.
 12. The method according to any preceding claim, wherein the second condition controlling a cell's transmission through the switch to a certain output is extended to include frame priority deadlock prevention by defining a frame to be “active” according if and only if its highest priority is being transmitted, so that said second condition allows a cell's transmission if and only if the output queue associated to said certain output has not exceeded its pretermined threshold OR said cell is marked “active” for said certain output, i.e. belonging to the highest priority of an “active frame” whose start-of-frame cell has been transmitted, but not its end-of-frame cell.
 13. A fixed-length cell routing switch providing routing capability for variable-length cell traffic with a shared memory, characterized in that each address of said memory includes storage space for one cell, and an associated multicast counter, thus, when a cell arrives, providing means for storing the cell's data at an available memory address, storing said used address in each destination output queue, and counting and storing the number of destinations in said counter.
 14. The routing switch according to claim 13, further including a plurality of registers, each associated with a particular input and a particular output of said switch for storing an indication, preferably a bit, indicating that said particular output is “active” with respect to said particular input, said indication being set when a start-of-frame cell of a specific frame received on said particular input is transmitted on said particular output and said specific frame being the last copy to be transmitted, and said indication being reset when the corresponding end-of-frame cell is transmitted at said particular output.
 15. The routing switch according to claim 13 or 14, further including means for assigning a priority to a frame to be transmitted and means for interrupting and/or resuming transmission of cells of a frame with a lower priority whenever a frame with a higher priority is to be transmitted at the same output.
 16. The routing switch according to claim 13, further including a plurality of registers, each associated with a particular priority, a particular input, and a particular output of said switch for storing an indication, preferably a bit, indicating that said particular output is “active” with respect to said particular input and said particular priority, said indication being set when a start-of-frame cell of a specific frame of said particular priority, received on said particular input, is transmitted on said particular output and said specific frame being the last copy to be transmitted, and said indication being reset when the corresponding end-of-frame cell is transmitted at said particular output. a plurality of registers, each associated with a particular priority, a particular input, and a particular output of said switch for storing an indication, preferably a bit, indicating that said particular output is “transmit active” with respect to said particular input and said particular priority, said indication being set when either a cell of a specific frame of said particular priority, received on said particular input, has been transmitted on said particular output in the current packet cycle, or no cell has been transmitted at all on said particular output, and said indication being reset otherwise. 